System and method for preserving a minority protocol name in a multiple protocol migration

ABSTRACT

A method, computer program product, and computer system for creating, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. Minority protocol name information associated with the first directory entry using the majority protocol may be relayed to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. A second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session may be created on the destination side. The name of the second directory entry created using the majority protocol may be reset to the minority protocol name created using the minority protocol name information cached on the destination side.

BACKGROUND

During an incremental copy stage of a multiple protocol migration, users may use, e.g., CIFS or NFS protocol to operate their file system. If the user use CIFS, then the system may call CIFS the majority protocol, and call the other protocol NFS the minority protocol. Some operations like “create file”, “create directory”, “rename”, “create soft link”, and “create hard link” should have name inputted, and they may be referred to as “name operations”. The “name operations” are generally sent to the migration source server first before they are performed on destination server. Generally, the minority name of a file is same as the majority name, but in some special cases they are different because different protocols have different name restrictions.

BRIEF SUMMARY OF DISCLOSURE

In one example implementation, a method, performed by one or more computing devices, may include but is not limited to creating, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. Minority protocol name information associated with the first directory entry using the majority protocol may be relayed to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. A second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session may be created on the destination side. The name of the second directory entry created using the majority protocol may be reset to the minority protocol name created using the minority protocol name information cached on the destination side.

One or more of the following example features may be included. Resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side may include sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side. Sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side may be sent in response to a remote procedure message sent to the source side from the destination side. The majority protocol may be Network File System (NFS) and the minority protocol may be Common Internet File System (CIFS). Sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to an access control list message sent to the source side from the destination side. The majority protocol may be CIFS and the minority protocol may be NFS. A remote procedure call may be bound for each session of the multi-protocol delta copy migration session.

In another example implementation, a computing system may include one or more processors and one or more memories configured to perform operations that may include but are not limited to creating a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. Minority protocol name information associated with the first directory entry using the majority protocol may be relayed to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. A second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session may be created on the destination side. The name of the second directory entry created using the majority protocol may be reset to the minority protocol name created using the minority protocol name information cached on the destination side.

One or more of the following example features may be included. Resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side may include sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side. Sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side may be sent in response to a remote procedure message sent to the source side from the destination side. The majority protocol may be Network File System (NFS) and the minority protocol may be Common Internet File System (CIFS). Sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to an access control list message sent to the source side from the destination side. The majority protocol may be CIFS and the minority protocol may be NFS. A remote procedure call may be bound for each session of the multi-protocol delta copy migration session.

In another example implementation, a computer program product may reside on a computer readable storage medium having a plurality of instructions stored thereon which, when executed across one or more processors, may cause at least a portion of the one or more processors to perform operations that may include but are not limited to creating a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. Minority protocol name information associated with the first directory entry using the majority protocol may be relayed to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. A second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session may be created on the destination side. The name of the second directory entry created using the majority protocol may be reset to the minority protocol name created using the minority protocol name information cached on the destination side.

One or more of the following example features may be included. Resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side may include sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side. Sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side may be sent in response to a remote procedure message sent to the source side from the destination side. The majority protocol may be Network File System (NFS) and the minority protocol may be Common Internet File System (CIFS). Sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to an access control list message sent to the source side from the destination side. The majority protocol may be CIFS and the minority protocol may be NFS. A remote procedure call may be bound for each session of the multi-protocol delta copy migration session.

The details of one or more example implementations are set forth in the accompanying drawings and the description below. Other possible example features and/or possible example advantages will become apparent from the description, the drawings, and the claims. Some implementations may not have those possible example features and/or possible example advantages, and such possible example features and/or possible example advantages may not necessarily be required of some implementations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example diagrammatic view of a protocol naming process coupled to an example distributed computing network according to one or more example implementations of the disclosure;

FIG. 2 is an example diagrammatic view of a storage system of FIG. 1 according to one or more example implementations of the disclosure;

FIG. 3 is an example diagrammatic view of a storage target of FIG. 1 according to one or more example implementations of the disclosure;

FIG. 4 is an example directory for a NFS name and CIFS name mapping;

FIG. 5 is an example diagrammatic view of an inconsistency table;

FIG. 6 is an example flowchart of a protocol naming process according to one or more example implementations of the disclosure;

FIG. 7 is an example is an example alternative view of a flowchart of a protocol naming process according to one or more example implementations of the disclosure; and

FIG. 8 is an example is an example alternative view of a flowchart of a protocol naming process according to one or more example implementations of the disclosure.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

System Overview:

In some implementations, the present disclosure may be embodied as a method, system, or computer program product. Accordingly, in some implementations, the present disclosure may take the form of an entirely hardware implementation, an entirely software implementation (including firmware, resident software, micro-code, etc.) or an implementation combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, in some implementations, the present disclosure may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.

In some implementations, any suitable computer usable or computer readable medium (or media) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer-usable, or computer-readable, storage medium (including a storage device associated with a computing device or client electronic device) may be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a digital versatile disk (DVD), a static random access memory (SRAM), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, a media such as those supporting the internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable medium could even be a suitable medium upon which the program is stored, scanned, compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of the present disclosure, a computer-usable or computer-readable, storage medium may be any tangible medium that can contain or store a program for use by or in connection with the instruction execution system, apparatus, or device.

In some implementations, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. In some implementations, such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. In some implementations, the computer readable program code may be transmitted using any appropriate medium, including but not limited to the internet, wireline, optical fiber cable, RF, etc. In some implementations, a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

In some implementations, computer program code for carrying out operations of the present disclosure may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java®, Smalltalk, C++ or the like. Java® and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. However, the computer program code for carrying out operations of the present disclosure may also be written in conventional procedural programming languages, such as the “C” programming language, PASCAL, or similar programming languages, as well as in scripting languages such as Javascript, PERL, or Python. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the internet using an Internet Service Provider). In some implementations, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGAs) or other hardware accelerators, micro-controller units (MCUs), or programmable logic arrays (PLAs) may execute the computer readable program instructions/code by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

In some implementations, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus (systems), methods and computer program products according to various implementations of the present disclosure. Each block in the flowchart and/or block diagrams, and combinations of blocks in the flowchart and/or block diagrams, may represent a module, segment, or portion of code, which comprises one or more executable computer program instructions for implementing the specified logical function(s)/act(s). These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the computer program instructions, which may execute via the processor of the computer or other programmable data processing apparatus, create the ability to implement one or more of the functions/acts specified in the flowchart and/or block diagram block or blocks or combinations thereof. It should be noted that, in some implementations, the functions noted in the block(s) may occur out of the order noted in the figures (or combined or omitted). For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

In some implementations, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks or combinations thereof.

In some implementations, the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed (not necessarily in a particular order) on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts (not necessarily in a particular order) specified in the flowchart and/or block diagram block or blocks or combinations thereof.

Referring now to the example implementation of FIG. 1, there is shown protocol naming process 10 that may reside on and may be executed by a computer (e.g., computer 12), which may be connected to a network (e.g., network 14) (e.g., the internet or a local area network). Examples of computer 12 (and/or one or more of the client electronic devices noted below) may include, but are not limited to, a storage system (e.g., a Network Attached Storage (NAS) system, a Storage Area Network (SAN)), a personal computer(s), a laptop computer(s), mobile computing device(s), a server computer, a series of server computers, a mainframe computer(s), or a computing cloud(s). As is known in the art, a SAN may include one or more of the client electronic devices, including a Redundant Array of Inexpensive Disks/Redundant Array of Independent Disks (RAID) device and a NAS system. In some implementations, each of the aforementioned may be generally described as a computing device. In certain implementations, a computing device may be a physical or virtual device. In many implementations, a computing device may be any device capable of performing operations, such as a dedicated processor, a portion of a processor, a virtual processor, a portion of a virtual processor, portion of a virtual device, or a virtual device. In some implementations, a processor may be a physical processor or a virtual processor. In some implementations, a virtual processor may correspond to one or more parts of one or more physical processors. In some implementations, the instructions/logic may be distributed and executed across one or more processors, virtual or physical, to execute the instructions/logic. Computer 12 may execute an operating system, for example, but not limited to, Microsoft® Windows®; Mac® OS X®; Red Hat® Linux®, Windows® Mobile, Chrome OS, Blackberry OS, Fire OS, or a custom operating system. (Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries or both; Mac and OS X are registered trademarks of Apple Inc. in the United States, other countries or both; Red Hat is a registered trademark of Red Hat Corporation in the United States, other countries or both; and Linux is a registered trademark of Linus Torvalds in the United States, other countries or both).

In some implementations, as will be discussed below in greater detail, a protocol naming process, such as protocol naming process 10 of FIG. 1, may create, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. Minority protocol name information associated with the first directory entry using the majority protocol may be relayed to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. A second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session may be created on the destination side. The name of the second directory entry created using the majority protocol may be reset to the minority protocol name created using the minority protocol name information cached on the destination side.

In some implementations, the instruction sets and subroutines of protocol naming process 10, which may be stored on storage device, such as storage device 16, coupled to computer 12, may be executed by one or more processors and one or more memory architectures included within computer 12. In some implementations, storage device 16 may include but is not limited to: a hard disk drive; all forms of flash memory storage devices; a tape drive; an optical drive; a RAID array (or other array); a random access memory (RAM); a read-only memory (ROM); or combination thereof. In some implementations, storage device 16 may be organized as an extent, an extent pool, a RAID extent (e.g., an example 4D+1P R5, where the RAID extent may include, e.g., five storage device extents that may be allocated from, e.g., five different storage devices), a mapped RAID (e.g., a collection of RAID extents), or combination thereof.

In some implementations, network 14 may be connected to one or more secondary networks (e.g., network 18), examples of which may include but are not limited to: a local area network; a wide area network or other telecommunications network facility; or an intranet, for example. The phrase “telecommunications network facility,” as used herein, may refer to a facility configured to transmit, and/or receive transmissions to/from one or more mobile client electronic devices (e.g., cellphones, etc.) as well as many others.

In some implementations, computer 12 may include a data store, such as a database (e.g., relational database, object-oriented database, triplestore database, etc.) and may be located within any suitable memory location, such as storage device 16 coupled to computer 12. In some implementations, data, metadata, information, etc. described throughout the present disclosure may be stored in the data store. In some implementations, computer 12 may utilize any known database management system such as, but not limited to, DB2, in order to provide multi-user access to one or more databases, such as the above noted relational database. In some implementations, the data store may also be a custom database, such as, for example, a flat file database or an XML database. In some implementations, any other form(s) of a data storage structure and/or organization may also be used. In some implementations, protocol naming process 10 may be a component of the data store, a standalone application that interfaces with the above noted data store and/or an applet/application that is accessed via client applications 22, 24, 26, 28. In some implementations, the above noted data store may be, in whole or in part, distributed in a cloud computing topology. In this way, computer 12 and storage device 16 may refer to multiple devices, which may also be distributed throughout the network.

In some implementations, computer 12 may execute a storage management application (e.g., storage management application 21), examples of which may include, but are not limited to, e.g., a storage system application, a cloud computing application, a data synchronization application, a data migration application, a garbage collection application, or other application that allows for the implementation and/or management of data in a clustered (or non-clustered) environment (or the like). In some implementations, protocol naming process 10 and/or storage management application 21 may be accessed via one or more of client applications 22, 24, 26, 28. In some implementations, protocol naming process 10 may be a standalone application, or may be an applet/application/script/extension that may interact with and/or be executed within storage management application 21, a component of storage management application 21, and/or one or more of client applications 22, 24, 26, 28. In some implementations, storage management application 21 may be a standalone application, or may be an applet/application/script/extension that may interact with and/or be executed within protocol naming process 10, a component of protocol naming process 10, and/or one or more of client applications 22, 24, 26, 28. In some implementations, one or more of client applications 22, 24, 26, 28 may be a standalone application, or may be an applet/application/script/extension that may interact with and/or be executed within and/or be a component of protocol naming process 10 and/or storage management application 21. Examples of client applications 22, 24, 26, 28 may include, but are not limited to, e.g., a storage system application, a cloud computing application, a data synchronization application, a data migration application, a garbage collection application, or other application that allows for the implementation and/or management of data in a clustered (or non-clustered) environment (or the like), a standard and/or mobile web browser, an email application (e.g., an email client application), a textual and/or a graphical user interface, a customized web browser, a plugin, an Application Programming Interface (API), or a custom application. The instruction sets and subroutines of client applications 22, 24, 26, 28, which may be stored on storage devices 30, 32, 34, 36, coupled to client electronic devices 38, 40, 42, 44, may be executed by one or more processors and one or more memory architectures incorporated into client electronic devices 38, 40, 42, 44.

In some implementations, one or more of storage devices 30, 32, 34, 36, may include but are not limited to: hard disk drives; flash drives, tape drives; optical drives; RAID arrays; random access memories (RAM); and read-only memories (ROM). Examples of client electronic devices 38, 40, 42, 44 (and/or computer 12) may include, but are not limited to, a personal computer (e.g., client electronic device 38), a laptop computer (e.g., client electronic device 40), a smart/data-enabled, cellular phone (e.g., client electronic device 42), a notebook computer (e.g., client electronic device 44), a tablet, a server, a television, a smart television, a smart speaker, an Internet of Things (IoT) device, a media (e.g., video, photo, etc.) capturing device, and a dedicated network device. Client electronic devices 38, 40, 42, 44 may each execute an operating system, examples of which may include but are not limited to, Android™, Apple® iOS®, Mac® OS X®; Red Hat® Linux®, Windows® Mobile, Chrome OS, Blackberry OS, Fire OS, or a custom operating system.

In some implementations, one or more of client applications 22, 24, 26, 28 may be configured to effectuate some or all of the functionality of protocol naming process 10 (and vice versa). Accordingly, in some implementations, protocol naming process 10 may be a purely server-side application, a purely client-side application, or a hybrid server-side/client-side application that is cooperatively executed by one or more of client applications 22, 24, 26, 28 and/or protocol naming process 10.

In some implementations, one or more of client applications 22, 24, 26, 28 may be configured to effectuate some or all of the functionality of storage management application 21 (and vice versa). Accordingly, in some implementations, storage management application 21 may be a purely server-side application, a purely client-side application, or a hybrid server-side/client-side application that is cooperatively executed by one or more of client applications 22, 24, 26, 28 and/or storage management application 21. As one or more of client applications 22, 24, 26, 28, protocol naming process 10, and storage management application 21, taken singly or in any combination, may effectuate some or all of the same functionality, any description of effectuating such functionality via one or more of client applications 22, 24, 26, 28, protocol naming process 10, storage management application 21, or combination thereof, and any described interaction(s) between one or more of client applications 22, 24, 26, 28, protocol naming process 10, storage management application 21, or combination thereof to effectuate such functionality, should be taken as an example only and not to limit the scope of the disclosure.

In some implementations, one or more of users 46, 48, 50, 52 may access computer 12 and protocol naming process 10 (e.g., using one or more of client electronic devices 38, 40, 42, 44) directly through network 14 or through secondary network 18. Further, computer 12 may be connected to network 14 through secondary network 18, as illustrated with phantom link line 54. Protocol naming process 10 may include one or more user interfaces, such as browsers and textual or graphical user interfaces, through which users 46, 48, 50, 52 may access protocol naming process 10.

In some implementations, the various client electronic devices may be directly or indirectly coupled to network 14 (or network 18). For example, client electronic device 38 is shown directly coupled to network 14 via a hardwired network connection. Further, client electronic device 44 is shown directly coupled to network 18 via a hardwired network connection. Client electronic device 40 is shown wirelessly coupled to network 14 via wireless communication channel 56 established between client electronic device 40 and wireless access point (i.e., WAP) 58, which is shown directly coupled to network 14. WAP 58 may be, for example, an IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, Wi-Fi®, RFID, and/or Bluetooth™ (including Bluetooth™ Low Energy) device that is capable of establishing wireless communication channel 56 between client electronic device 40 and WAP 58. Client electronic device 42 is shown wirelessly coupled to network 14 via wireless communication channel 60 established between client electronic device 42 and cellular network/bridge 62, which is shown by example directly coupled to network 14.

In some implementations, some or all of the IEEE 802.11x specifications may use Ethernet protocol and carrier sense multiple access with collision avoidance (i.e., CSMA/CA) for path sharing. The various 802.11x specifications may use phase-shift keying (i.e., PSK) modulation or complementary code keying (i.e., CCK) modulation, for example. Bluetooth™ (including Bluetooth™ Low Energy) is a telecommunications industry specification that allows, e.g., mobile phones, computers, smart phones, and other electronic devices to be interconnected using a short-range wireless connection. Other forms of interconnection (e.g., Near Field Communication (NFC)) may also be used.

In some implementations, various I/O requests (e.g., I/O request 15) may be sent from, e.g., client applications 22, 24, 26, 28 to, e.g., computer 12. Examples of I/O request 15 may include but are not limited to, data write requests (e.g., a request that content be written to computer 12) and data read requests (e.g., a request that content be read from computer 12).

Data Storage System:

Referring also to the example implementation of FIGS. 2-3 (e.g., where computer 12 may be configured as a data storage system), computer 12 may include storage processor 100 and a plurality of storage targets (e.g., storage targets 102, 104, 106, 108, 110). In some implementations, storage targets 102, 104, 106, 108, 110 may include any of the above-noted storage devices. In some implementations, storage targets 102, 104, 106, 108, 110 may be configured to provide various levels of performance and/or high availability. For example, storage targets 102, 104, 106, 108, 110 may be configured to form a non-fully-duplicative fault-tolerant data storage system (such as a non-fully-duplicative RAID data storage system), examples of which may include but are not limited to: RAID 3 arrays, RAID 4 arrays, RAID 5 arrays, and/or RAID 6 arrays. It will be appreciated that various other types of RAID arrays may be used without departing from the scope of the present disclosure.

While in this particular example, computer 12 is shown to include five storage targets (e.g., storage targets 102, 104, 106, 108, 110), this is for example purposes only and is not intended limit the present disclosure. For instance, the actual number of storage targets may be increased or decreased depending upon, e.g., the level of redundancy/performance/capacity required.

Further, the storage targets (e.g., storage targets 102, 104, 106, 108, 110) included with computer 12 may be configured to form a plurality of discrete storage arrays. For instance, and assuming for example purposes only that computer 12 includes, e.g., ten discrete storage targets, a first five targets (of the ten storage targets) may be configured to form a first RAID array and a second five targets (of the ten storage targets) may be configured to form a second RAID array.

In some implementations, one or more of storage targets 102, 104, 106, 108, 110 may be configured to store coded data (e.g., via storage management process 21), wherein such coded data may allow for the regeneration of data lost/corrupted on one or more of storage targets 102, 104, 106, 108, 110. Examples of such coded data may include but is not limited to parity data and Reed-Solomon data. Such coded data may be distributed across all of storage targets 102, 104, 106, 108, 110 or may be stored within a specific storage target.

Examples of storage targets 102, 104, 106, 108, 110 may include one or more data arrays, wherein a combination of storage targets 102, 104, 106, 108, 110 (and any processing/control systems associated with storage management application 21) may form data array 112.

The manner in which computer 12 is implemented may vary depending upon e.g., the level of redundancy/performance/capacity required. For example, computer 12 may be configured as a SAN (i.e., a Storage Area Network), in which storage processor 100 may be, e.g., a dedicated computing system and each of storage targets 102, 104, 106, 108, 110 may be a RAID device. An example of storage processor 100 may include but is not limited to a VPLEX™, VNX™, TRIDENT™, or Unity™ system offered by Dell EMC™ of Hopkinton, Mass.

In the example where computer 12 is configured as a SAN, the various components of computer 12 (e.g., storage processor 100, and storage targets 102, 104, 106, 108, 110) may be coupled using network infrastructure 114, examples of which may include but are not limited to an Ethernet (e.g., Layer 2 or Layer 3) network, a fiber channel network, an InfiniBand network, or any other circuit switched/packet switched network.

As discussed above, various I/O requests (e.g., I/O request 15) may be generated. For example, these I/O requests may be sent from, e.g., client applications 22, 24, 26, 28 to, e.g., computer 12. Additionally/alternatively (e.g., when storage processor 100 is configured as an application server or otherwise), these I/O requests may be internally generated within storage processor 100 (e.g., via storage management process 21). Examples of I/O request 15 may include but are not limited to data write request 116 (e.g., a request that content 118 be written to computer 12) and data read request 120 (e.g., a request that content 118 be read from computer 12).

In some implementations, during operation of storage processor 100, content 118 to be written to computer 12 may be received and/or processed by storage processor 100 (e.g., via storage management process 21). Additionally/alternatively (e.g., when storage processor 100 is configured as an application server or otherwise), content 118 to be written to computer 12 may be internally generated by storage processor 100 (e.g., via storage management process 21).

As discussed above, the instruction sets and subroutines of storage management application 21, which may be stored on storage device 16 included within computer 12, may be executed by one or more processors and one or more memory architectures included with computer 12. Accordingly, in addition to being executed on storage processor 100, some or all of the instruction sets and subroutines of storage management application 21 (and/or protocol naming process 10) may be executed by one or more processors and one or more memory architectures included with data array 112.

In some implementations, storage processor 100 may include front end cache memory system 122. Examples of front end cache memory system 122 may include but are not limited to a volatile, solid-state, cache memory system (e.g., a dynamic RAM cache memory system), a non-volatile, solid-state, cache memory system (e.g., a flash-based, cache memory system), and/or any of the above-noted storage devices.

In some implementations, storage processor 100 may initially store content 118 within front end cache memory system 122. Depending upon the manner in which front end cache memory system 122 is configured, storage processor 100 (e.g., via storage management process 21) may immediately write content 118 to data array 112 (e.g., if front end cache memory system 122 is configured as a write-through cache) or may subsequently write content 118 to data array 112 (e.g., if front end cache memory system 122 is configured as a write-back cache).

In some implementations, one or more of storage targets 102, 104, 106, 108, 110 may include a backend cache memory system. Examples of the backend cache memory system may include but are not limited to a volatile, solid-state, cache memory system (e.g., a dynamic RAM cache memory system), a non-volatile, solid-state, cache memory system (e.g., a flash-based, cache memory system), and/or any of the above-noted storage devices.

Storage Targets:

As discussed above, one or more of storage targets 102, 104, 106, 108, 110 may be a RAID device. For instance, and referring also to FIG. 3, there is shown example target 150, wherein target 150 may be one example implementation of a RAID implementation of, e.g., storage target 102, storage target 104, storage target 106, storage target 108, and/or storage target 110. An example of target 150 may include but is not limited to a VPLEX™, VNX™, TRIDENT™, or Unity™ system offered by Dell EMC™ of Hopkinton, Mass. Examples of storage devices 154, 156, 158, 160, 162 may include one or more electro-mechanical hard disk drives, one or more solid-state/flash devices, and/or any of the above-noted storage devices. It will be appreciated that while the term “disk” or “drive” may be used throughout, these may refer to and be used interchangeably with any types of appropriate storage devices as the context and functionality of the storage device permits.

In some implementations, target 150 may include storage processor 152 and a plurality of storage devices (e.g., storage devices 154, 156, 158, 160, 162). Storage devices 154, 156, 158, 160, 162 may be configured to provide various levels of performance and/or high availability (e.g., via storage management process 21). For example, one or more of storage devices 154, 156, 158, 160, 162 (or any of the above-noted storage devices) may be configured as a RAID 0 array, in which data is striped across storage devices. By striping data across a plurality of storage devices, improved performance may be realized. However, RAID 0 arrays may not provide a level of high availability. Accordingly, one or more of storage devices 154, 156, 158, 160, 162 (or any of the above-noted storage devices) may be configured as a RAID 1 array, in which data is mirrored between storage devices. By mirroring data between storage devices, a level of high availability may be achieved as multiple copies of the data may be stored within storage devices 154, 156, 158, 160, 162.

While storage devices 154, 156, 158, 160, 162 are discussed above as being configured in a RAID 0 or RAID 1 array, this is for example purposes only and not intended to limit the present disclosure, as other configurations are possible. For example, storage devices 154, 156, 158, 160, 162 may be configured as a RAID 3, RAID 4, RAID 5 or RAID 6 array.

While in this particular example, target 150 is shown to include five storage devices (e.g., storage devices 154, 156, 158, 160, 162), this is for example purposes only and not intended to limit the present disclosure. For instance, the actual number of storage devices may be increased or decreased depending upon, e.g., the level of redundancy/performance/capacity required.

In some implementations, one or more of storage devices 154, 156, 158, 160, 162 may be configured to store (e.g., via storage management process 21) coded data, wherein such coded data may allow for the regeneration of data lost/corrupted on one or more of storage devices 154, 156, 158, 160, 162. Examples of such coded data may include but are not limited to parity data and Reed-Solomon data. Such coded data may be distributed across all of storage devices 154, 156, 158, 160, 162 or may be stored within a specific storage device.

The manner in which target 150 is implemented may vary depending upon e.g., the level of redundancy/performance/capacity required. For example, target 150 may be a RAID device in which storage processor 152 is a RAID controller card and storage devices 154, 156, 158, 160, 162 are individual “hot-swappable” hard disk drives. Another example of target 150 may be a RAID system, examples of which may include but are not limited to an NAS (i.e., Network Attached Storage) device or a SAN (i.e., Storage Area Network).

In some implementations, storage target 150 may execute all or a portion of storage management application 21. The instruction sets and subroutines of storage management application 21, which may be stored on a storage device (e.g., storage device 164) coupled to storage processor 152, may be executed by one or more processors and one or more memory architectures included with storage processor 152. Storage device 164 may include but is not limited to any of the above-noted storage devices.

As discussed above, computer 12 may be configured as a SAN, wherein storage processor 100 may be a dedicated computing system and each of storage targets 102, 104, 106, 108, 110 may be a RAID device. Accordingly, when storage processor 100 processes data requests 116, 120, storage processor 100 (e.g., via storage management process 21) may provide the appropriate requests/content (e.g., write request 166, content 168 and read request 170) to, e.g., storage target 150 (which is representative of storage targets 102, 104, 106, 108 and/or 110).

In some implementations, during operation of storage processor 152, content 168 to be written to target 150 may be processed by storage processor 152 (e.g., via storage management process 21). Storage processor 152 may include cache memory system 172. Examples of cache memory system 172 may include but are not limited to a volatile, solid-state, cache memory system (e.g., a dynamic RAM cache memory system) and/or a non-volatile, solid-state, cache memory system (e.g., a flash-based, cache memory system). During operation of storage processor 152, content 168 to be written to target 150 may be received by storage processor 152 (e.g., via storage management process 21) and initially stored (e.g., via storage management process 21) within front end cache memory system 172.

During an incremental copy stage of a multiple protocol migration, users may use, e.g., CIFS or NFS protocol to operate their file system. If the user use CIFS, then the system may call CIFS the majority protocol, and call the other protocol NFS the minority protocol. Some operations like “create file”, “create directory”, “rename”, “create soft link”, and “create hard link” should have name inputted, and they may be referred to as “name operations”. The “name operations” are generally sent to the migration source server first before they are performed on destination server. Generally, the minority name of a file is same as the majority name, but in some special cases they are different because different protocols have different name restrictions.

For example, FIG. 4 shows a directory 400 for a NFS name and CIFS name mapping. Assume that the NFS protocol names are case sensitive while the CIFS protocol names are not. Further assume that NFS protocol names support some special characters, e.g., V:*?“

|, while CIFS protocol names do not. Further assume that CIFS protocol names support surrogate pairs, while some old NFS systems do not, and these systems will treat surrogate pairs as the character “_”. The resulting minority names will be created by minority protocol rules with majority names as inputs, as shown in table 400.

Since the source and destination of some types of migration (e.g., IMT migration) are different systems, and they also may have different file directory structures during migration, although eventually they may be the same, this may cause, in some cases, a node with the NFS name “ABCabc.txt” may have the CIFS name “ABCabc˜1.txt” on the source but have the CIFS name “ABCabc˜2.txt” on the destination, which is not acceptable for IMT migration.

For example, during the initial copy phase, the user may create ABCabc.txt in an empty folder dir1 from the NFS client, and this file will be synced to the destination. When user deletes this file, this delete operation will not be synced to the destination since its initial copy phase. In a delta copy phase, the user creates a new file ABCABC.txt. Before creating this file, the source dir1 is empty and the destination dir1 has a file ABCabc.txt.

From above examples, it is now clear that because of the protocols' behavior, the rules mapping from majority names to minority names are not strictly a 1:1 mapping, as the minority names can be uncertain in some cases, and a node with NFS name “ABCabc.txt” may have CIFS name “ABCabc˜1.txt” or “ABCabc˜3.txt”, etc., which means the source server and the destination server can be inconsistent, which is not acceptable in migration. Therefore, as will be discussed further below, to prevent inconsistent of minority protocol name between the source and the destination server, the present disclosure may provide a mechanism to preserve the minority protocol names from the source, and then reset the minority name on the destination side by the preserved names. As a result, the present disclosure may, for example, guarantee the minority protocol names are consistent between migration source and destination.

It will be appreciated that if the system were to just simply use the majority protocol name to create the minority protocol name on both sides, the number at the suffix of the minority name generated by the protocol will be uncertain, and it is also related with some history operations before migration. For sure, inconsistencies between source side and destination side will bring trouble, and as can be seen by the resulting inconsistencies table 500 in FIG. 5. Moreover, if the user cancelled the migration, some file names will change from the minority protocol client.

The Protocol Naming Process:

As discussed above and referring also at least to the example implementations of FIGS. 6-8, protocol naming (PN) process 10 may create 600, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. PN process 10 may relay 602 minority protocol name information associated with the first directory entry using the majority protocol to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side. PN process 10 may create 604 a second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session on the destination side. PN process 10 may reset 606 the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side.

In some implementations, the majority protocol may be Network File System (NFS) and the minority protocol may be Common Internet File System (CIFS) (referring to the example flowchart 700 implementation of FIG. 7), and in some implementations, the majority protocol may be CIFS and the minority protocol may be NFS (referring to the example flowchart 800 implementation of FIG. 8). It will be appreciated that flowcharts 700 and 800 may be followed similar or alternative views of the flowchart in FIG. 6. It will also be appreciated that various other protocols may also be used without departing from the scope of the present disclosure. As such, the use of the particular protocols being used as majority and/or minority protocols should be taken as example only and not to otherwise limit the scope of the present disclosure. As will be discussed in greater detail below, the destination may receive an operation request that will create a new majority protocol name directory entry. The operation may be applied to the source file system which creates a directory entry for majority protocol name. The minority protocol name may be queried from the source directory entry on the source file system. The operation may be applied to the destination file system which creates a directory entry for majority protocol name. The minority protocol name may be set on the destination directory entry on the destination file system. It will be appreciated that the creation of a new directory entry does not necessarily mean a file has been created. Furthermore, it will be appreciated that a directory entry does not necessarily relate to a file (as it could refer to a directory, symbolic link, alternate data stream, socket and so on).

Assume for example purposes only that with a multi-protocol file system, a file may have two names, one may be a CIFS name (Windows name), the other may be a NFS name (Unix name), In a migration session, the two file names generally must be identical on both the source side and the destination side. As will be discussed below, for the NFS client on the destination (with NFS being the majority protocol), PN process 10 may use a Remote Procedure Call (RPC) to get CIFS (minority protocol) name after PN process 10 performed the naming operations on the source side, and caches it in memory. After performing the operations on the destination side, PN process 10 may reset the minority name to the cached minority name created on source side.

For example, in some implementations, PN process 10 may create 600, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation may be done on a source side for a multi-protocol delta copy migration session. For example, assume NFS is the majority protocol and CIFS is the minority protocol. In step 1 of FIG. 7, during a multi-protocol delta-copy migration session, a user (e.g., via PN process 10) may create a directory entry named, e.g., a:b.txt from the NFS client. Here, the minority protocol is CIFS.

In some implementations, PN process 10 may relay 602 minority protocol name information associated with the first directory entry using the majority protocol to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information may be cached on the destination side. For example, in step 2 of FIG. 7, the destination side (e.g., via PN process 10) may relay this NFS (create) operation to source side. The source side (e.g., via PN process 10) may create the directory entry a:b.txt, and generate a CIFS name. Because CIFS does not support “:” in the name, the source side (e.g., via PN process 10) may generate an alternative name, for example “a_b˜1.txt”, if “a_b˜1.txt” already existed on source side, the CIFS name could be “a_b˜2.txt”.

In step 3 of FIG. 7, if there is no error on step 2, the source side (e.g., via PN process 10) may reply “OK” with the new file handle to the destination side.

As will be discussed further below, PN process 10 may reset 606 the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side. For instance, as will be discussed in greater detail below, in some implementations, resetting 606 the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side may include sending 608 the minority protocol name information of the first directory entry created using the minority protocol to the destination side, where in some implementations, sending 608 the minority protocol name information of the first directory entry created using the minority protocol to the destination side may be sent in response to a remote procedure message sent to the source side from the destination side. For example, in step 4 of FIG. 7, since the NFS protocol does not support getting CIFS name in an NFS call, with the above-noted new directory entry handle, the destination side (e.g., via PN process 10) may create a RPC message and send to the source side to get the CIFS directory entry name.

Continuing with the above example, in step 5 of FIG. 7, the source side (e.g., via PN process 10) may reply to the RPC message with the created CIFS name, for example, the CIFS name “a_b˜2.txt”, and the destination side (e.g., via PN process 10) may parse it from the reply message and cache the CIFS name in memory (or other storage device).

In some implementations, PN process 10 may create 604 a second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session on the destination side. For example, in step 6 of FIG. 7, the destination side (e.g., via PN process 10) may create the directory entry a:b.txt, which also has the CIFS name, which might be different than the source side.

In some implementations, PN process 10 may reset 606 the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side. For example, in step 7 of FIG. 7, the destination side (e.g., via PN process 10) may reset the CIFS name with the cached CIFS name in step 5. After this step, the CIFS name of both source and destination sides will be the same. As such, at this point, the user (e.g., via PN process 10) has successfully created a directory entry which has a NFS name a:b.txt and a CIFS name: a_b˜2.txt.

As noted above, in some implementations, the majority protocol may be CIFS and the minority protocol may be NFS, as shown in the flowchart of FIG. 8. As will be discussed further below, for a CIFS client, PN process 10 may use the CIFS operation “get ACL” (Access Control List) to fetch the Unix name as the NFS minority name. Similar to FIG. 7, PN process 10 may cache it and reset the minority name on the destination side.

For example, in step 1 of FIG. 8, during multi-protocol delta-copy migration session, the user (e.g., via PN process 10) may create a directory entry named “φabc.txt” from the CIFS client, where here the minority protocol is NFS.

In step 2 of FIG. 8, the destination side (e.g., via PN process 10) may relay this CIFS operation to source side. The source side (e.g., via PN process 10) may create the directory entry φabc.txt, and generate a NFS name. Because NFS does not support surrogate pair character “φ” in the name, the source side (e.g., via PN process 10) may generate an alternative name, for example “_abc˜1.txt”, if “_abc˜1.txt” already existed on source side, and the NFS name could be “_abc˜2.txt”.

In step 3 of FIG. 8, if there are no errors on step two, the source side (e.g., via PN process 10) may reply “OK” with the new directory entry handle to the destination side.

In some implementations, sending 608 the minority protocol name information of the first directory entry created using the minority protocol to the destination side may be sent in response to an access control list message sent to the source side from the destination side. For example, in step 4 of FIG. 8, the destination side may (e.g., via PN process 10) form a get-ACL (Access Control List) message and send it to the source side to get the NFS directory entry name.

In step 5 of FIG. 8, the source side (e.g., via PN process 10) may reply to the get-ACL message with the NFS directory entry name, for example “_abc˜2.txt”.

In step 6 of FIG. 8, the destination side (e.g., via PN process 10) may parse the NFS directory entry name from the reply message to get the NFS directory entry name and cache it to memory (or other storage device).

In step 7 of FIG. 8, the destination side (e.g., via PN process 10) may create the directory entry φabc.txt, which also has a NFS name, which might be different than the source side.

In step 8 of FIG. 8, the destination side (e.g., via PN process 10) may reset the NFS name with the cached NFS name in step 6. After this step, the NFS name of both sides will be the same (in this example, the NFS name “_abc˜2.txt).

In some implementations, PN process 10 may optionally bind 610 a remote procedure call for each session of the multi-protocol delta copy migration session. For example, for each migration session, PN process 10 may bind a RPC connection, and for operations from different clients, PN process 10 may share several RPC clients in a round robin fashion (or other technique). PN process 10 may give a system parameter for the number of clients that PN process 10 may adjust any time.

Regarding the above-noted potential errors, some error handling may be needed. For instance, in some implementations, before migration, PN process 10 may check if the RPC service (XATTRP) is available on the source side, and if not, PN process 10 may decline the migration. If getting the minority name failed, the operation will succeed anyway just using the minority name before the reset. However, PN process 10 may fail the node and give an alert. If the failure reason is a time out, PN process 10 may reconnect the RPC continuously with set or random intervals. If the reconnect succeeds, PN process 10 may resync the failed the node, and the migration session will back to normal.

In some implementations, the present disclosure may help to correctly synchronize the minority protocol names during migration. Users may always use the same minority name without confusion, even if they cancel the migration session, making the file system more robust. The cost to do so may be very low, and the mechanism may only increase one request-response via RPC or one CIFS “get ACL” message. Should the “get ACL” message already be used during the normal operation, PN process 10 may just reuse it.

The terminology used herein is for the purpose of describing particular implementations only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. As used herein, the language “at least one of A, B, and C” (and the like) should be interpreted as covering only A, only B, only C, or any combination of the three, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps (not necessarily in a particular order), operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps (not necessarily in a particular order), operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents (e.g., of all means or step plus function elements) that may be in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications, variations, substitutions, and any combinations thereof will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The implementation(s) were chosen and described in order to explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various implementation(s) with various modifications and/or any combinations of implementation(s) as are suited to the particular use contemplated.

Having thus described the disclosure of the present application in detail and by reference to implementation(s) thereof, it will be apparent that modifications, variations, and any combinations of implementation(s) (including any modifications, variations, substitutions, and combinations thereof) are possible without departing from the scope of the disclosure defined in the appended claims. 

What is claimed is:
 1. A computer-implemented method comprising: creating, by a computing device, a first directory entry with a name using a majority protocol, wherein the creation is done on a source side for a multi-protocol delta copy migration session; relaying minority protocol name information associated with the first directory entry using the majority protocol to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side; creating a second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session on the destination side; and resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side.
 2. The computer-implemented method of claim 1 wherein resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side includes sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side.
 3. The computer-implemented method of claim 2 wherein sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to a remote procedure message sent to the source side from the destination side.
 4. The computer-implemented method of claim 3 wherein the majority protocol is Network File System (NFS) and the minority protocol is Common Internet File System (CIFS).
 5. The computer-implemented method of claim 2 wherein sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to an access control list message sent to the source side from the destination side.
 6. The computer-implemented method of claim 5 wherein the majority protocol is CIFS and the minority protocol is NFS.
 7. The computer-implemented method of claim 1 further comprising binding a remote procedure call for each session of the multi-protocol delta copy migration session.
 8. A computer program product residing on a computer readable storage medium having a plurality of instructions stored thereon which, when executed across one or more processors, causes at least a portion of the one or more processors to perform operations comprising: creating a first directory entry with a name using a majority protocol, wherein the creation is done on a source side for a multi-protocol delta copy migration session; relaying minority protocol name information associated with the first directory entry using the majority protocol to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side; creating a second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session on the destination side; and resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side.
 9. The computer program product of claim 8 wherein resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side includes sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side.
 10. The computer program product of claim 9 wherein sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to a remote procedure message sent to the source side from the destination side.
 11. The computer program product of claim 10 wherein the majority protocol is Network File System (NFS) and the minority protocol is Common Internet File System (CIFS).
 12. The computer program product of claim 9 wherein sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to an access control list message sent to the source side from the destination side.
 13. The computer program product of claim 12 wherein the majority protocol is CMS and the minority protocol is NFS.
 14. The computer program product of claim 8 wherein the operations further comprise binding a remote procedure call for each session of the multi-protocol delta copy migration session.
 15. A computing system including one or more processors and one or more memories configured to perform operations comprising: creating a first directory entry with a name using a majority protocol, wherein the creation is done on a source side for a multi-protocol delta copy migration session; relaying minority protocol name information associated with the first directory entry using the majority protocol to a destination side for the multi-protocol delta copy migration session, wherein the minority protocol name information is cached on the destination side; creating a second directory entry with the name using the majority protocol for the multi-protocol delta copy migration session on the destination side; and resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side.
 16. The computing system of claim 15 wherein resetting the name of the second directory entry created using the majority protocol to the minority protocol name created using the minority protocol name information cached on the destination side includes sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side.
 17. The computing system of claim 16 wherein sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to a remote procedure message sent to the source side from the destination side.
 18. The computing system of claim 17 wherein the majority protocol is Network File System (NFS) and the minority protocol is Common Internet File System (CIFS).
 19. The computing system of claim 16 wherein sending the minority protocol name information of the first directory entry created using the minority protocol to the destination side is sent in response to an access control list message sent to the source side from the destination side when the majority protocol is CIFS and the minority protocol is NFS.
 20. The computing system of claim 15 wherein the operations further comprise binding a remote procedure call for each session of the multi-protocol delta copy migration session. 